Member
April 18, 2026

Problem Framing A Methodological Framework

1. The nature of problem framing

Problem framing is not the same as problem solving. It is the prior and more consequential act of determining what the problem actually is before any solution is attempted. In most practical contexts, this distinction is collapsed: a difficulty is felt, a solution is reached for, and the gap between them — the actual structure of the problem — is never made explicit. The consequences of that collapse are predictable. Solutions address symptoms. Root causes persist. Effort is expended on constraints that were never binding.

This document describes problem framing as a structured, sequential methodology: a two-stage filtration process that moves from a felt difficulty to a precisely framed, high-leverage question ready for creative intervention. The methodology integrates three intellectual traditions into a single coherent arc, and produces a chain of outputs — each sharpening the previous — that terminates in a validated problem statement calibrated for divergent ideation.

1.1 What a frame is

A frame is not a solution, and it is not a permanent definition. It is a temporary structural interpretation of a difficulty: a description of the gap that exists, the cause that is most responsible for it, and the question that opens the gap to creative intervention. Frames are provisional by nature. The methodology described here builds in explicit moments of revision — not as a concession to uncertainty, but because co-evolution of problem understanding and solution understanding is how complex problems are actually resolved.

A frame has four properties that distinguish it from a vague sense of difficulty:

• It is structural, not personal. A frame describes conditions and processes, not failures of individuals.

• It is measurable. Both the current state and the goal state can be described in terms that allow verification — someone not involved in the situation could confirm whether the gap has closed.

• It is bounded. The frame identifies a cause that is within the actor's sphere of influence — deep enough to be meaningful, close enough to be actionable.

• It is open. The final form of a well-constructed frame is a question, not a statement — an invitation to innovate rather than a verdict on a difficult situation.

1.2 The central failure modes

Three failure modes recur across problem-framing attempts in practice. Each produces a different kind of wasted effort:

Failure mode 1: solving the wrong problem

The difficulty is real, but the gap it represents either does not exist in measurable terms, does not align with the actor’s primary goal, or would not significantly improve the situation if closed. Energy is spent on problems worth complaining about rather than problems worth solving.

Failure mode 2: solving the right problem at the wrong cause

The gap is genuine, but effort is distributed equally across all plausible causes rather than concentrated on the highest-leverage constraint. Because impact is always more concentrated than causes, this produces the sensation of effort without proportionate progress.

Failure mode 3: a frame that forecloses rather than opens

The problem is correctly identified and the root cause accurately located, but the final problem statement is posed as a fact rather than a question, or as a question so narrow that it already contains the solution. The creative phase is blocked before it begins.

2. Intellectual lineage

The methodology integrates three bodies of work. Each contributes a distinct and necessary element. Understanding the lineage clarifies why the framework is structured as it is, and what would be lost if any of the three elements were removed.

Source	Core principle	Application in this framework
Goldratt — Theory of Constraints	System throughput is governed by a single binding constraint. Improving a non-constraint yields no system improvement.	The Problems Worth Solving filter: a gap must be confirmed as a real constraint before any problem-solving energy is spent.
Srijan Sanchar — ABC Analysis	Impact is always more concentrated than effort. A singular AAA cause can drive up to 49% of a gap’s total impact.	The cause-prioritisation filter applied after gap confirmation. Directs analytical effort to the highest-leverage constraint within the gap.
Exploratory Framing philosophy	Design problems are progressively constructed, not discovered once. Frames co-evolve with understanding. Tolerance of ambiguity is a trainable competency.	The philosophical premise underlying the entire framework: every output is the best current frame, not a final answer. Structural iteration is built in.

2.1 Theory of Constraints — the strategic premise

Goldratt's Theory of Constraints established that in any system, throughput is governed not by average capacity but by a single binding constraint. Improving any part of the system except its constraint produces zero improvement in system output. The practical implication is radical: before any improvement effort begins, the constraint must be correctly identified. Effort expended elsewhere is, by definition, wasted.

Applied to problem framing, this principle licenses the pre-analytical filter: before framing begins, verify that a genuine constraint exists. A difficulty without a definable goal state is not a constraint — it is a preference. A constraint that, if removed, would not advance the primary goal is not the binding constraint. The Problems Worth Solving filter is the direct application of this logic.

2.2 ABC Analysis — cause prioritisation

Srijan Sanchar's ABC Analysis refines the classic Pareto principle at the level of causes within a confirmed gap. The Pareto insight — that a small number of causes is responsible for a disproportionate share of effects — is widely cited but rarely operationalised with precision in problem-framing practice. ABC Analysis makes it operational.

The model identifies five tiers of cause by their estimated impact on the gap. The defining claim is that a singular AAA cause — representing as little as 1% of all identifiable causes — can drive up to 49% of the gap's total impact. This is not a statistical law but a directional principle: impact concentration is always greater than intuition suggests, and naming the highest-leverage cause before analytical effort begins is the difference between focused and scattered inquiry.

2.3 Exploratory framing — the epistemological premise

The exploratory framing perspective, drawn from design cognition research, contributes the epistemological premise that underlies the framework's structure. Its central claim is that problem understanding and solution understanding co-evolve: they do not occur in sequence, with problem definition completed before solution search begins. Instead, each step of analysis produces new understanding that reshapes the frame.

Three consequences follow for the methodology:

• Frames must be treated as temporary. Any output at any stage is the best current frame, not a final one. Revision is expected, not exceptional.

• Iteration must be built in structurally. A methodology that provides no explicit moment for frame revision will produce premature closure. The Reframe Checkpoint in this framework is the structural response to this requirement.

• Tolerance of ambiguity is a competency, not a disposition. The ability to act on a provisional frame without certainty is learnable and improvable. The methodology creates repeated practice of this competency across each stage.

3. The framework — stage by stage

The methodology proceeds through seven stages arranged as a two-phase structure: a pre-analytical filtration phase and an analytical framing phase. The pre-analytical phase determines whether the problem is worth solving and which cause is highest-leverage. The analytical phase frames that cause with increasing precision until it becomes an actionable question.

The sequence as a whole:

Stage	Process step	Output carried forward
F1	Problems Worth Solving filter — verify that a measurable gap exists between a current state and a goal state	Confirmed gap statement
F2	ABC Analysis — enumerate causes, estimate relative impact, identify the AAA cause	Named AAA cause (hypothesis)
1	Gap Analysis Model — formalise current state, goal state, and barrier in precise structural language	Sharpened gap statement
2	Multi-Perspective Synthesis — rotate the problem through stakeholder lenses, surface hidden variables	Expanded barrier understanding
RC	Reframe Checkpoint — revisit AAA cause in light of new perspectives, revise if warranted	Confirmed or revised AAA cause
3	Why-Why Analysis with Actionable Boundaries — drill to root cause, stop at sphere-of-influence boundary	Sweet-spot root cause
4	HMW Reframe — convert root cause to an open, calibrated How Might We question	Validated HMW question — ready for divergent ideation

Filter 1 — Problems worth solving

Goldratt-derived gap verification

Pre-analytical

Principle

Not every difficulty is a problem worth solving. A problem worth solving is defined specifically: it is a measurable gap between a Current State and a Goal State that, if closed, meaningfully advances the primary goal. Problems that cannot be described in these terms are preferences or grievances. They do not proceed through the framework.

The test has two components:

• Current State test: can the existing condition be described in observable, verifiable terms — without interpretation, attribution, or evaluation?

• Goal State test: can the desired outcome be described as a measurable or observable condition specific enough that one could verify whether it had been achieved?

If both components can be stated with sufficient precision, a gap exists. If either is vague, the difficulty has not yet been formulated as a problem. The filter requires clarification before proceeding.

The TOC connection

Goldratt demonstrated that effort spent improving a non-constraint produces zero system improvement. The Problems Worth Solving filter applies this logic at the identification stage: unless a genuine constraint can be named — a definable gap between current reality and a specific goal — there is no constraint to improve. Effort applied elsewhere is structurally wasted, regardless of its quality or quantity.

Key terms

Current state

Goal state

Measurable gap

Binding constraint

Filter 2 — ABC Analysis

Cause prioritisation — identifying the AAA constraint

Pre-analytical

Principle

Once a gap is confirmed, the natural response is to enumerate all plausible causes and address them comprehensively. This is the wrong response. Cause impact is always more concentrated than the number of causes suggests: a small number of causes is responsible for a disproportionate share of the gap's existence. Distributing effort equally across all causes wastes most of it on the trivial many.

ABC Analysis operationalises this insight. Each identified cause is evaluated for its estimated individual impact on the gap — that is, if this cause alone were removed, what proportion of the gap would close? Causes are then ranked by this estimate and classified into five tiers:

Tier	Impact	Description
AAA	49%	The singular critical cause. Removing it alone closes the largest share of the gap.
AA	30%	High-leverage secondary causes. Worth addressing after the AAA.
A	13%	Contributing causes with meaningful but limited individual impact.
B	6%	Minor contributors. Low return on focused effort.
C	2%	The trivial many. Creative energy spent here yields negligible system improvement.

The highest-ranked cause becomes the candidate AAA cause: the single constraint within the gap on which analytical and creative effort will be concentrated. This is a hypothesis, not a verdict. The subsequent perspective rotation in Stage 2 of the analytical phase will test and potentially revise it.

Critical note on the impact figures

The percentage figures are directional anchors, not empirical measurements. They encode the principle that impact concentration is always greater than intuition suggests. The practical instruction is: estimate relative impact, rank causes, and name the top candidate. The exact percentages matter less than the discipline of ranking before deciding where to focus.

Provisional status of the AAA cause

The AAA cause identified at this stage is formed from the analyst’s current perspective and available information. It should be explicitly treated as a hypothesis. The multi-perspective rotation in Stage 2 of the analytical phase will almost certainly introduce information that reshapes this ranking. That revision is not a sign of failure in the pre-analytical work — it is evidence that the framework is functioning correctly.

Key terms

AAA cause

Impact concentration

Trivial many

High-leverage constraint

Stage 1 — Gap Analysis Model

Formalising the structural description of the problem

Analytical phase

Principle

The gap confirmed in the pre-analytical phase now requires formal structural description. The Gap Analysis Model converts a felt or informally described difficulty into a precise three-part statement that can be handed to any stakeholder and understood without further explanation.

The three components of the model are:

• Current State — the existing condition in observable, verifiable terms. Not an interpretation, not an attribution of cause, not an evaluation. A description of what can be seen or measured now.

• Goal State — the desired condition as a measurable or observable success metric. Specific enough that the question “have we arrived?” has an unambiguous answer.

• Barrier — the specific structural condition preventing the transition from current to goal state. This is the problem. Not the current state itself, not a symptom of the barrier, not a cause of the barrier — but the barrier: the structural obstacle that keeps the gap open.

The discipline of this model is in the distinctions it enforces. The current state is not the problem; it is the starting position. The goal state is not the solution; it is the destination. The barrier is the problem — and naming it as a structural condition rather than a personal failure is what makes it tractable.

The structural imperative

A barrier framed as a personal failing — “people do not care,” “the culture is resistant” — produces helplessness. A barrier framed as a structural condition — “there is no mechanism for X to occur before Y is required” — is a specification for design. The Gap Analysis Model enforces structural language because structural problems have structural solutions.

Key terms

Current state

Goal state

Barrier

Structural framing

Stage 2 — Multi-Perspective Synthesis

Rotating the problem through stakeholder lenses to surface hidden variables

Analytical phase

Principle

A problem framed from a single perspective is a partial problem. Complex gaps are rarely one-dimensional: the same barrier looks different when viewed from different positions within the system. A condition that appears to be a motivation problem from one position may appear to be a resource constraint from another, a process failure from a third, and a communication gap from a fourth. Each perspective reveals variables invisible to the others.

Multi-Perspective Synthesis expands the frame by systematically rotating the problem through the perspectives of all significant stakeholders. The goal is not to collect all perspectives simultaneously — it is to inhabit each one genuinely enough to discover what it reveals that the analyst’s default lens conceals.

The cognitive trap that this stage addresses is functional fixedness: the tendency to understand a problem exclusively through the lens of familiar roles, tools, and categories. This tendency makes the analyst blind to solutions that require a frame the analyst has never occupied. Genuine perspective-taking — not surface acknowledgement of other views, but arguing from within them — is what breaks this constraint.

The distinction between listing and inhabiting perspectives

Listing perspectives (“from the customer’s perspective, they are frustrated”) is not perspective synthesis. It is the analyst’s interpretation of another person’s experience, filtered through the analyst’s existing frame. Inhabiting a perspective means arguing from within it in first person: what is actually happening for this stakeholder, in their own terms, that creates or sustains the barrier? The discomfort of this exercise is the signal that it is working.

After the rotation, the barrier statement from Stage 1 should be reviewed. If a new perspective has revealed a more accurate or more complete structural description of the barrier, the statement should be revised before proceeding. This revised barrier feeds directly into the Reframe Checkpoint.

Key terms

Stakeholder matrix

Perspective rotation

Functional fixedness

Hidden variables

Reframe Checkpoint

Structural iteration — revise the AAA cause in light of new perspectives

Built-in iteration loop

Principle

This stage exists because of a structural truth about how understanding evolves in complex problem-solving: the initial framing is always formed under conditions of incomplete information. The perspective rotation in Stage 2 introduces information the pre-analytical phase did not have. That new information will frequently reveal that the AAA cause identified in Filter 2 was either incomplete or aimed at the wrong level of the causal structure.

The Reframe Checkpoint converts the framework from a single forward pass into a process with one deliberate return loop. Its sole question is: given what the perspective rotation revealed, is the previously identified AAA cause still the highest-leverage constraint? If yes, the analysis proceeds with confirmation. If no, the AAA cause is revised before the root cause drill begins.

Why this stage is not optional

A framework without an explicit iteration stage treats the pre-analytical AAA identification as a commitment rather than a hypothesis. This produces the first failure mode in reverse: the analyst correctly identified a high-leverage cause before gaining perspective, then fails to revise it after gaining perspective. The consequence is a root cause drill aimed at a cause that the analyst now has reason to believe is not the binding constraint. The Reframe Checkpoint is the structural prevention of this failure.

The checkpoint operates at two levels:

• Individual revision: does the new perspective information change which cause has the highest estimated impact on the gap?

• Framing revision: does the new perspective information change the structural description of the barrier itself — not just which cause is highest but what the barrier actually is?

Either or both may require revision. The output of the checkpoint is a confirmed or revised AAA cause, now tested against multiple perspectives rather than a single one.

Key terms

Temporary framing

Co-evolution

Iteration loop

Revised AAA cause

Stage 3 — Why-Why Analysis with Actionable Boundaries

Root cause drilling within the sphere of influence

Analytical phase

Principle

With a perspective-tested AAA cause confirmed, the analysis now drills into its structural origins. The 5-why method — asking “why does this cause exist?” repeatedly until a root cause is reached — is a well-established diagnostic tool. Its standard application, however, contains a structural flaw: there is no boundary rule. Unconstrained drilling produces root causes that exist entirely outside the analyst’s capacity to change them.

The Principle of Actionable Boundaries solves this problem by introducing two complementary concepts:

• Sphere of Influence — the bounded domain within which the analyst has the power to act, directly or indirectly. Causes that exist outside this sphere cannot be the basis for a framing that leads to action.

• The Sweet Spot — the deepest layer of causal analysis that remains within the sphere of influence. A cause at the sweet spot is meaningful (deep enough to address a genuine structural condition) and actionable (close enough to be changed by someone in the analyst’s position).

At each layer of the why-why drill, the cause is classified on a three-point scale:

• Within sphere of influence — the analyst can change this directly.

• Partially within sphere of influence — the analyst can influence but not determine this.

• Outside sphere of influence — systemic, policy-level, or structural conditions the analyst cannot change from their current position.

When the drill reaches a cause classified as outside the sphere of influence, it has gone too far. The preceding layer — the deepest cause still within reach — is the sweet spot. This becomes the root cause for framing purposes.

The two drilling failure modes

Stopping too early: the drill halts at the surface symptom — effectively restating the barrier from Stage 1 rather than revealing its structural origin. The framing produced has insufficient depth to generate solutions that address the underlying condition.

Overshooting: the drill continues past the sphere of influence into systemic conditions the analyst cannot change. The root cause identified is accurate but unactionable. Any HMW question built on it will generate solutions that require system-level authority the analyst does not have.

Key terms

5-why analysis

Root cause

Sphere of influence

Actionable sweet spot

Stage 4 — The “How Might We” Reframe

Converting the root cause into an actionable, open-ended question

Analytical phase

Principle

A well-constructed frame should not terminate as a statement. Statements close; questions open. The purpose of the entire preceding analysis is to identify, with maximum precision, the structural condition that most constrains the system — and then to convert that condition into an invitation to innovate.

The How Might We (HMW) format performs this conversion. The phrasing carries deliberate structural meaning:

• “How” asserts that the problem is solvable. It positions the framing as the beginning of a path forward, not the documentation of an impasse.

• “Might” holds the solution space open. It does not presuppose an approach. Multiple solutions, of meaningfully different kinds, remain possible.

• “We” distributes ownership. The challenge is not an individual burden but a shared problem that can draw on collective intelligence.

A correctly calibrated HMW question occupies a specific zone on a breadth axis. It must be narrow enough to provide direction — the question should exclude large classes of irrelevant solutions — and broad enough to allow multiple meaningfully different approaches. The calibration test is simple: can a person not involved in the preceding analysis generate at least three distinct solution ideas from the question in under two minutes? If yes, the question is well-calibrated. If they generate only one approach or cannot generate any, the question is either too narrow or too broad.

Calibration failure	What it looks like	Correction
Too broad	The question generates solutions across entirely disconnected domains with no common logic	Add a constraint from the root cause that focuses the domain without specifying the method
Too narrow	The question implies a single solution; all generated responses are variations of the same approach	Remove the implied method and frame the underlying challenge the method was addressing
Solution-contaminated	The question names a specific method or tool, foreclosing the ideation phase before it begins	Ask: what challenge is this method attempting to solve? Frame that challenge instead

Key terms

HMW question

Breadth calibration

Solution contamination

Divergent thinking trigger

4. The output chain

Each stage of the framework produces a specific artefact. These artefacts are not independent deliverables — they form a chain in which each output becomes the direct input to the following stage. Understanding the chain is important because it makes visible what is lost if any stage is skipped: not merely the benefit of that stage, but the correct input to every stage that follows.

Stage	Artefact produced	What is lost if this stage is skipped
F1	Confirmed gap statement	The subsequent analysis has no verified target. The AAA cause, root cause, and HMW question may all be aimed at a difficulty that either does not exist in measurable terms or would not advance the primary goal even if resolved.
F2	Named AAA cause (hypothesis)	The analytical phase has no prioritised entry point. The why-why drill begins without knowing which cause is highest-leverage, producing a well-executed analysis aimed at a sub-optimal constraint.
1	Sharpened gap statement with precise barrier language	The perspective rotation in Stage 2 has no precise structural description to test. Perspectives are rotated around a vague sense of difficulty rather than a specified barrier, reducing the likelihood of discovering genuinely hidden variables.
2	Expanded understanding of barrier from multiple positions	The Reframe Checkpoint has no new information to test the AAA cause against. The cause identified in Filter 2 proceeds without perspective testing, preserving whatever functional fixedness shaped the pre-analytical work.
RC	Confirmed or revised AAA cause, perspective-tested	The why-why drill is aimed at a cause that has not been tested against alternative perspectives. If Filter 2's initial AAA identification was wrong, the error propagates uncorrected into the root cause and the HMW question.
3	Sweet-spot root cause within sphere of influence	The HMW question is built on either a surface symptom (drill stopped too early) or an unactionable systemic condition (drill overshot). Solutions generated will address either the wrong level or conditions that cannot be changed.
4	Validated HMW question calibrated for divergent ideation	The analytical work terminates as a statement of difficulty rather than an invitation to innovate. The creative phase begins without a frame, producing scattered ideation rather than focused generative inquiry.

5. The epistemological stance

The framework described in the preceding sections rests on a specific epistemological position that should be stated explicitly, because it determines how every stage is interpreted and how the outputs should be held.

5.1 Frames are provisional, not permanent

Every artefact produced by this framework — the gap statement, the AAA cause, the barrier statement, the root cause, the HMW question — is the best current frame, not a final answer. This is not a concession to uncertainty but a reflection of how complex problems actually work. The frame co-evolves with the understanding that each stage generates. The Reframe Checkpoint is the single explicit revision point built into the framework, but the disposition of provisional framing applies at every stage.

The practical consequence is that revision is not a sign of failure. A practitioner who leaves the Reframe Checkpoint with a different AAA cause than they entered with has not wasted the pre-analytical work. They have used it correctly — as a hypothesis that was tested and found to need refinement. A practitioner who never revises anything across the entire framework should ask whether each stage was genuinely interrogated or merely passed through.

5.2 Ambiguity tolerance as a core competency

The methodology requires the practitioner to act on incomplete information at every stage. The gap statement is formed before the cause is known. The AAA cause is named before the perspectives of other stakeholders have been gathered. The root cause is identified before the solution space has been explored. At each point, the practitioner must hold a provisional frame firmly enough to proceed and loosely enough to revise.

This is the competency of ambiguity tolerance: the ability to act with direction in the absence of certainty. It is not a personality trait but a practice, developed through repeated structured experience of exactly this kind of provisional commitment followed by principled revision. The framework creates that experience by design.

5.3 The relationship between analytical rigour and creative openness

There is an apparent tension in the framework: its pre-analytical and analytical stages are highly structured and directional, while its final output — the HMW question — is deliberately open and multi-directional. This tension is not a design flaw; it is the framework's core logic.

Analytical rigour is what makes creative openness productive. A broadly open question built on a vague sense of difficulty generates scattered and shallow responses. The same broadly open question built on a perspective-tested, sphere-of-influence-bounded, precisely located root cause generates focused and actionable responses. The structure of the analysis is what makes the openness of the question generative rather than merely permissive.

In this sense, the framework's deepest claim is that precision and creativity are not in tension — precision in problem framing is the precondition for creativity in problem solving.

Problem Framing — A Methodological Framework

Srijan Sanchar

Intellectual lineage: Goldratt · Srijan Sanchar ABC Analysis · Exploratory Framing philosophy